home *** CD-ROM | disk | FTP | other *** search
- Path: news.nyu.edu!schonberg!dewar
- From: dewar@cs.nyu.edu (Robert Dewar)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.edu
- Subject: Re: ANSI C and POSIX (was Re: C/C++ knocks the crap out of Ada)
- Date: 7 Apr 1996 08:27:37 -0400
- Organization: Courant Institute of Mathematical Sciences
- Message-ID: <dewar.828879781@schonberg>
- References: <JSA.96Feb16135027@organon.com> <emery-0204960656230001@line030.nwm.mindlink.net> <828632277snz@genesis.demon.co.uk> <dewar.828704810@schonberg> <4k3utg$ndp@solutions.solon.com> <dewar.828757752@schonberg> <danpop.828819479@rscernix>
- NNTP-Posting-Host: schonberg.cs.nyu.edu
- X-Newsreader: NN version 6.5.0 (NOV)
-
- Dan Pop
-
- "This is plain nonsense. read in Linux (or anywhere else) CANNOT be ANSI
- compliant for the simple reason that the ANSI/ISO C standard does NOT
- define such a function. read may (or may not) be POSIX, SVID or XPG
- "
-
- Dan, you miss the point, of course read in Linux is compliant with the
- ANSI standard, precisely because this standard does NOT specify any
- required behavior for read, and permits the addition of such functions.
-
- How could you possibly claim that read could be non-compliant with ANSI
- (something is either compliant or non-compliant, we do not have three
- valued logic here).
-
- It would be interesting to know more details about Unix validation. I
- guess the point here is that most systems that people think of as Unix
- are actually NOT called Unix (e.g. Linux, IRIX, AIX, Solaris), and so
- you have to be very careful in understanding what this validation means.
- I guess the issue here is IPR protection rather than propagation of an
- open standard.
-
- Precisely which commonly used Unix-like systems have been certified by
- the copyright holder in this manner?
-
- Can someone who does know the details enlighten here?
-
-
-